Configuration Management

You can use Configuration Management to create configuration profiles within Lighthouse that you can associate with Opengear devices/nodes during and after enrollment. When you update those profiles, changes can be committed down to the nodes in a short period of time.

This enables you to centrally configure, monitor, and manage nodes through Lighthouse’s hierarchy profile driven approach using group profiles.

To allow nodes to use Configuration Management:

  • For new devices that you are enrolling into the system, you use the profile name and bundle token for call home enrollment.

  • For existing nodes, you can use the link functionality on the Nodes page.

  • OM and CM Opengear devices must be on at least version 25.11.

Note: This feature is being rolled out. This release contains the core functionality for the feature with additional functionality to roll out in future releases.

Profile Syncing

When another user modifies and saves a profile that you are viewing, you are shown an alert that prompts you to accept updates from the other user. It is highly recommended that you click Accept to reload the profile you are viewing with the updates. If you do not accept the updates, you may overwrite them when you save your updates.

If another user deletes the profile, you are redirected to the top-level profile and shown an alert.

Hierarchy

Profiles are created in a hierarchy which is displayed in the hierarchy view. There is always one base profile at the top level. Below this base profile, you can create however many profiles you want, but you can only create a maximum of six levels deep (five levels in addition to the base profile).

When you create a child profile, it automatically inherits values from the parent profile. These values can be overridden at any level in the hierarchy, see Inheritance and Overriding.

Inheritance and Overriding

The following rules apply to inherited and overridden values:

  • Overridden values take precedence.

  • For values that are inherited as part of a list, you can only add new list items. You cannot change or remove the inherited items.

The following icons display next to fields:

  • when a new value has been added.

  • when an inherited value has been overridden.

Configuration Sections

You can add the following configuration sections to a profile using the Configuration Selector:

  • Profile Summary: Use this section to configure basic profile information like name. device type, and enrollment settings. This is the default section and is always visible.

  • Authentication: Use this section to configure remote authentication settings for devices.

You can move between configuration sections without saving.

Adding Configuration Sections

You can add a new Configuration Section to a profile at any level in the hierarchy. When added, the section is automatically added to all child profiles below the profile to which it is added.

To add more configuration sections to a profile:

  1. Click the   button located on the side of the Configuration Selector.
    The MANAGE CONFIG SECTIONS dialog displays.

  2. Select the check box for the section(s) you want to add.
    The Configuration Selector displays a section card for any selected sections.

When you select a section in the Configuration Selector, the appropriate fields for configuration display in the Configuration Section of the Configuration Management page.

Removing Configuration Sections

You can remove configuration sections:

  • in the same way that you add them, by deselecting the check boxes.

  • ONLY if the section was added at that level. A child profile cannot remove a Configuration Section if it was added or inherited from a parent.

When you remove a section:

  • Initially, the section card is removed from the Configuration Selector.

    Note: The configuration is only deleted when the profile is saved. If you re-select the section before you save the profile, the card and previously defined configuration reappears.

  • The section is removed from all child profiles below the profile from which it is removed.

Log File

The configuration management logs can be found in /var/log/config_management.log.